@benjimaclellan Would love your feedback on this and if any changes are required do let me know

@CodeMaverick2

Why are yu copying from others PR, kindly give some chance to other participants thank you Maintainer please take note while reviewing

@SecludedPerson700

I’m not sure what you mean. If you’re suggesting that I copied your PR, I’d encourage you to carefully review both submissions they are quite different, and mine directly addresses the requirements outlined in the issue.

I had discussed my implementation plan with the maintainer before starting work when no one had commented on the issue. I’ve also closed another issue in this repository, so I’m familiar with the expected standards.

Additionally, I’d recommend reviewing your own PR again it may help clarify how the issue requirements are intended to be solved.

If you have specific technical concerns, I’m happy to discuss them constructively. Let’s keep the conversation focused on the code and the actual requirements.

Making accusations without clear evidence isn’t productive, and difficulty in solving an issue isn’t a valid reason to blame others

@SecludedPerson700

I’m not sure what you mean. If you’re suggesting that I copied your PR, I’d encourage you to carefully review both submissions they are quite different, and mine directly addresses the requirements outlined in the issue.

I had discussed my implementation plan with the maintainer before starting work when no one had commented on the issue. I’ve also closed another issue in this repository, so I’m familiar with the expected standards.

Additionally, I’d recommend reviewing your own PR again it may help clarify how the issue requirements are intended to be solved.

If you have specific technical concerns, I’m happy to discuss them constructively. Let’s keep the conversation focused on the code and the actual requirements.

Making accusations without clear evidence isn’t productive, and difficulty in solving an issue isn’t a valid reason to blame others

maintainers kindly note while reviewing thank yu i will leave this to the maintainers

@learningdungeon @AbdullahKazi500 @ dhanaa abhirjk hey guys I would also suggesst checking yur work and pr if you made any contributions for the issue thnks again .

Hi @CodeMaverick2 - thanks for another PR! It looks great, and complements the previous bounty. I'm reviewing all the PRs currently before the end of the hackathon. My only comment from the video you posted (thanks for providing it!) is that the two-qubit gates, e.g., CNOT are not visualized what the second qubit register it acts on is.

I see no overlap in the code that was submitted between PRs for this bounty, and have provided feedback on each about how they solve the posted issue. In addition, all participants are allowed to submit multiple PRs.

@learningdungeon @AbdullahKazi500 @ dhanaa abhirjk hey guys I would also suggesst checking yur work and pr if you made any contributions for the issue thnks again .

please check main.py at https://github.com/learningdungeon/GATE

@benjimaclellan Thanks for the feedback! Updated the CNOT visualization both the control and target qubits are now shown on the circuit grid. Control qubit displays ●→{target} and target qubit displays ⊕←{control}, at the same time step. Clearing either end removes both.

Regarding the copying claims I had shared my implementation approach with you before anyone else commented on the issue, and this PR complements my earlier analog builder (#5). I appreciate you confirming there's no overlap. Happy to leave it at that and let the work speak for itself.

Demo -

@benjimaclellan Also fixed gate colors on the circuit grid each gate type now renders in its distinct color: - X = red
Z = blue
H = purple
CNOT = orange
I = grey